Photon-level light shifting for enhanced file system security and authenticity

ABSTRACT

An approach is provided in which the approach receives a request to upload a file at a server system that includes metadata encoded with a non-invertible key. The metadata includes contact information corresponding to an owner of the file. The approach establishes both a photon channel and a classical channel between the server system and a client system, which are both secured using one or more shared secret keys. The approach interfaces with the client system over the photon channel and the classical channel to decode the contact information at the server system, and sends an upload request from the server system to the owner of the file using the contact information. The approach authorizes the upload request at the server system in response to receiving an upload approval from the owner.

BACKGROUND

Security and privacy is important in today's digital world. Securitypertains to safeguarding user data whereas privacy pertains tosafeguarding a user's identity. Internet piracy and illegal file sharingare amongst many cybercrimes that have been, and continue to be aconcern. Internet piracy is the illegal act of distributing and or thereproduction of digital files that is traded over computer networks.These files include digital books, movies, PC games, hacked software,music and others.

File sharing is the practice of sharing computer data or space in anetwork on a computer network. Illegal file sharing is similar tointernet piracy in terms of distributing illegal copies of certain filesand products to others in a network. As the file is shared with theother party, the person receiving the file now has freedom to manipulateand/or trade the file with other users.

Classical computing refers to computing devices that manipulate ones andzeros to execute operations. Optical computing, or photonic computing,uses photons produced by lasers or diodes for computation. Photons haveshown promise to enable a higher bandwidth than the electrons used inclassical computing. Photonic logic is the use of photons (light) inlogic gates and switching is obtained using nonlinear optical effectswhen two or more signals are combined. A photon is a small particle oflight and is also referred to as a type of quantum (e.g., a tinyparticle). Fiber-optic communication is a method of transmitting photonsfrom one system to another system by sending pulses of infrared lightthrough an optical fiber.

BRIEF SUMMARY

According to one embodiment of the present disclosure, an approach isprovided in which the approach receives a request to upload a file at aserver system that includes metadata encoded with a non-invertible key.The metadata includes contact information corresponding to an owner ofthe file. The approach establishes both a photon channel and a classicalchannel between the server system and a client system, which are bothsecured using one or more shared secret keys. The approach interfaceswith the client system over the photon channel and the classical channelto decode the contact information at the server system, and sends anupload request from the server system to the owner of the file using thecontact information. The approach authorizes the upload request at theserver system in response to receiving an upload approval from theowner.

The foregoing is a summary and thus contains, by necessity,simplifications, generalizations, and omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the present disclosure,as defined solely by the claims, will become apparent in thenon-limiting detailed description set forth below.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The present disclosure may be better understood, and its numerousobjects, features, and advantages made apparent to those skilled in theart by referencing the accompanying drawings, wherein:

FIG. 1 is a block diagram of a data processing system in which themethods described herein can be implemented;

FIG. 2 provides an extension of the information handling systemenvironment shown in FIG. 1 to illustrate that the methods describedherein can be performed on a wide variety of information handlingsystems which operate in a networked environment;

FIG. 3 is an exemplary diagram showing a system that uses photonchannels and classical channels along with a non-invertible key exchangeprotocol to decode file owner information and request file uploadapproval from the file owner;

FIG. 4 is an exemplary diagram depicting encoded owner informationinserted into a file;

FIG. 5 is an exemplary flowchart showing steps taken by an owner systemto create a secure file and upload the secure file to a cloud network;

FIG. 6 is an exemplary flowchart showing steps taken by a serverEnhanced Security and Authenticity System (ESAS) to interface with afile owner to authenticate an upload of the file by an upload requestor;and

FIG. 7 is an exemplary flowchart showing steps taken by a server ESAS tointerface with a client ESAS to decode owner contact information.

DETAILED DESCRIPTION

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present disclosure has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the disclosure in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the disclosure. Theembodiment was chosen and described in order to best explain theprinciples of the disclosure and the practical application, and toenable others of ordinary skill in the art to understand the disclosurefor various embodiments with various modifications as are suited to theparticular use contemplated.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a computer, or other programmable data processing apparatusto produce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks. These computerreadable program instructions may also be stored in a computer readablestorage medium that can direct a computer, a programmable dataprocessing apparatus, and/or other devices to function in a particularmanner, such that the computer readable storage medium havinginstructions stored therein comprises an article of manufactureincluding instructions which implement aspects of the function/actspecified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be accomplished as one step, executed concurrently,substantially concurrently, in a partially or wholly temporallyoverlapping manner, or the blocks may sometimes be executed in thereverse order, depending upon the functionality involved. It will alsobe noted that each block of the block diagrams and/or flowchartillustration, and combinations of blocks in the block diagrams and/orflowchart illustration, can be implemented by special purposehardware-based systems that perform the specified functions or acts orcarry out combinations of special purpose hardware and computerinstructions. The following detailed description will generally followthe summary of the disclosure, as set forth above, further explainingand expanding the definitions of the various aspects and embodiments ofthe disclosure as necessary.

FIG. 1 illustrates information handling system 100, which is asimplified example of a computer system capable of performing thecomputing operations described herein. Information handling system 100includes one or more processors 110 coupled to processor interface bus112. Processor interface bus 112 connects processors 110 to Northbridge115, which is also known as the Memory Controller Hub (MCH). Northbridge115 connects to system memory 120 and provides a means for processor(s)110 to access the system memory. Graphics controller 125 also connectsto Northbridge 115. In one embodiment, Peripheral Component Interconnect(PCI) Express bus 118 connects Northbridge 115 to graphics controller125. Graphics controller 125 connects to display device 130, such as acomputer monitor.

Northbridge 115 and Southbridge 135 connect to each other using bus 119.In some embodiments, the bus is a Direct Media Interface (DMI) bus thattransfers data at high speeds in each direction between Northbridge 115and Southbridge 135. In some embodiments, a PCI bus connects theNorthbridge and the Southbridge. Southbridge 135, also known as theInput/Output (I/O) Controller Hub (ICH) is a chip that generallyimplements capabilities that operate at slower speeds than thecapabilities provided by the Northbridge. Southbridge 135 typicallyprovides various busses used to connect various components. These bussesinclude, for example, PCI and PCI Express busses, an ISA bus, a SystemManagement Bus (SMBus or SMB), and/or a Low Pin Count (LPC) bus. The LPCbus often connects low-bandwidth devices, such as boot ROM 196 and“legacy” I/O devices (using a “super I/O” chip). The “legacy” I/Odevices (198) can include, for example, serial and parallel ports,keyboard, mouse, and/or a floppy disk controller. Other components oftenincluded in Southbridge 135 include a Direct Memory Access (DMA)controller, a Programmable Interrupt Controller (PIC), and a storagedevice controller, which connects Southbridge 135 to nonvolatile storagedevice 185, such as a hard disk drive, using bus 184.

ExpressCard 155 is a slot that connects hot-pluggable devices to theinformation handling system. ExpressCard 155 supports both PCI Expressand Universal Serial Bus (USB) connectivity as it connects toSouthbridge 135 using both the USB and the PCI Express bus. Southbridge135 includes USB Controller 140 that provides USB connectivity todevices that connect to the USB. These devices include webcam (camera)150, infrared (IR) receiver 148, keyboard and trackpad 144, andBluetooth device 146, which provides for wireless personal area networks(PANs). USB Controller 140 also provides USB connectivity to othermiscellaneous USB connected devices 142, such as a mouse, removablenonvolatile storage device 145, modems, network cards, IntegratedServices Digital Network (ISDN) connectors, fax, printers, USB hubs, andmany other types of USB connected devices. While removable nonvolatilestorage device 145 is shown as a USB-connected device, removablenonvolatile storage device 145 could be connected using a differentinterface, such as a Firewire interface, etcetera.

Wireless Local Area Network (LAN) device 175 connects to Southbridge 135via the PCI or PCI Express bus 172. LAN device 175 typically implementsone of the Institute of Electrical and Electronic Engineers (IEEE)802.11 standards of over-the-air modulation techniques that all use thesame protocol to wirelessly communicate between information handlingsystem 100 and another computer system or device. Optical storage device190 connects to Southbridge 135 using Serial Analog Telephone Adapter(ATA) (SATA) bus 188. Serial ATA adapters and devices communicate over ahigh-speed serial link. The Serial ATA bus also connects Southbridge 135to other forms of storage devices, such as hard disk drives. Audiocircuitry 160, such as a sound card, connects to Southbridge 135 via bus158. Audio circuitry 160 also provides functionality associated withaudio hardware such as audio line-in and optical digital audio in port162, optical digital output and headphone jack 164, internal speakers166, and internal microphone 168. Ethernet controller 170 connects toSouthbridge 135 using a bus, such as the PCI or PCI Express bus.Ethernet controller 170 connects information handling system 100 to acomputer network, such as a Local Area Network (LAN), the Internet, andother public and private computer networks.

While FIG. 1 shows one information handling system, an informationhandling system may take many forms. For example, an informationhandling system may take the form of a desktop, server, portable,laptop, notebook, or other form factor computer or data processingsystem. In addition, an information handling system may take other formfactors such as a personal digital assistant (PDA), a gaming device,Automated Teller Machine (ATM), a portable telephone device, acommunication device or other devices that include a processor andmemory.

FIG. 2 provides an extension of the information handling systemenvironment shown in FIG. 1 to illustrate that the methods describedherein can be performed on a wide variety of information handlingsystems that operate in a networked environment. Types of informationhandling systems range from small handheld devices, such as handheldcomputer/mobile telephone 210 to large mainframe systems, such asmainframe computer 270. Examples of handheld computer 210 includepersonal digital assistants (PDAs), personal entertainment devices, suchas Moving Picture Experts Group Layer-3 Audio (MP3) players, portabletelevisions, and compact disc players. Other examples of informationhandling systems include pen, or tablet, computer 220, laptop, ornotebook, computer 230, workstation 240, personal computer system 250,and server 260. Other types of information handling systems that are notindividually shown in FIG. 2 are represented by information handlingsystem 280. As shown, the various information handling systems can benetworked together using computer network 200. Types of computer networkthat can be used to interconnect the various information handlingsystems include Local Area Networks (LANs), Wireless Local Area Networks(WLANs), the Internet, the Public Switched Telephone Network (PSTN),other wireless networks, and any other network topology that can be usedto interconnect the information handling systems. Many of theinformation handling systems include nonvolatile data stores, such ashard drives and/or nonvolatile memory. The embodiment of the informationhandling system shown in FIG. 2 includes separate nonvolatile datastores (more specifically, server 260 utilizes nonvolatile data store265, mainframe computer 270 utilizes nonvolatile data store 275, andinformation handling system 280 utilizes nonvolatile data store 285).The nonvolatile data store can be a component that is external to thevarious information handling systems or can be internal to one of theinformation handling systems. In addition, removable nonvolatile storagedevice 145 can be shared among two or more information handling systemsusing various techniques, such as connecting the removable nonvolatilestorage device 145 to a USB port or other connector of the informationhandling systems.

As discussed above, internet piracy and illegal file sharing arebecoming more and more of a concern. Unfortunately, today's approachesuse classical computing approaches to protect data and privacy, whichmalicious users are capable of hacking. For example, individual usersmay share digital soft copies of their personal and confidential filesover the internet for processing some of their applications. In thisexample, some of the digital soft copies may be circulated(intentionally or un-intentionally) and land in the hands of malicioususers who can misuse the original user's digital copies for illegaltransactions or create fake online accounts in commercial or socialplatforms.

FIGS. 3 through 7 depict an approach that can be executed on aninformation handling system that uses a combination of photon computingand classical computing to protect sensitive data utilized for uploadauthorization. A client enhanced security and authenticity system (ESAS)encodes owner information and a security flag with a non-invertible key.The client ESAS then embeds the encoded owner information into a fileand sends the file to a cloud network. When an upload site receives arequest to upload the file from a requestor, a server ESAS at the uploadsite interacts with the client ESAS over photon channels and classicalchannels to establish shared keys using a non-invertible key exchangeprotocol (KEP). Then, the server ESAS interfaces with the client systemover the photon channel and the classical channel using the shared keysto decode the contact information. In turn, the server ESAS sends anupload request to the owner using the contact information. The serverESAS receives a response from the owner and, upon approval, the serverESAS adds an “Authenticated” flag to the file and completes the upload.

FIG. 3 is an exemplary diagram showing a system that uses photonchannels and classical channels along with a non-invertible key exchangeprotocol to decode file owner information and request file uploadapproval from the file owner.

Owner system 300 includes client enhanced security and authenticitysystem (ESAS) 305, which interfaces with server ESAS 330 to ensure filescreated by the owner of owner system 300 are not maliciously uploaded.First, when the owner of owner system 300 wishes to upload a file tocloud network 318, client ESAS 305 proceeds through a series of steps tocreate secure file 310 by encoding metadata 315 with non-invertible key(NIK) 306 and embedding encoded metadata 315. A non-invertible key is akey where multiple y values can produce the same x value, and a user isrequired to know which x value to use to properly decode the metadata.In one embodiment, the metadata includes owner information, such as theowner's name and contact information, and a Security AuthenticityDetection Flag (SADF) discussed herein (see FIG. 4 and correspondingtext for further details).

Client ESAS 305 validates the owner information (e.g., third partyverification systems) and sets the SADF flag to “Enabled.” In turn,owner system 300 uploads secure file 310 with metadata 315 to cloudnetwork 318 and database directory 319 maintains a directory that mapsuploaded secure files with corresponding client ESAS IP addresses.

Then, at some point in the future, upload requesting system 320 wishesto upload secure file 310 to upload site 335 that includes server ESAS330. When upload site 335 receives upload request 322 from uploadrequesting system 330, upload site 335 detects the encoded metadata andinvokes server ESAS 330 to perform non-invertible key exchange protocol(KEP) 340 over classical channels and photon channels to establish ashared secret key; receive non-invertible key 306 from client ESAS 305over the photon channel; and decode the owner information in metadata315.

In one embodiment, server ESAS 330 and client ESAS 305 useexponentiation to exchange a secret key (e.g., Diffie-Hellman) thatencrypts/decrypts through invertible multiplication (e.g., ElGamal). Inanother embodiment, the non-invertible KEP 340 is aimed to establish ashared secret key (ks) between client ESAS 305 and server ESAS 330through a public channel in the presence of a malicious user. In thisembodiment, numbers {pxaka,qyaka,n} and {pxbkb,qybkb,n} along with primenumbers p, q and r are publicly known by client ESAS 305 and server ESAS330. The values {xi,ki} constitutes a private key of client ESAS 305 andserver ESAS 330, respectively. In this embodiment, client ESAS 305 andserver ESAS 330 agree to use a module n, so they compute the integersand exchange them through a public channel. Client ESAS 305 and serverESAS 330 perform two operations (e.g., exponentiation andmultiplication) over the numbers received. Then, client ESAS 305 andserver ESAS 330 apply Euler's theorem to the results of the twooperations. Client ESAS 305 sends to server ESAS 330 the resulting valuepxbxaqybya*kb mod n who applies kb⁻¹ to derive the number pxbxaqybya*modn. Similarly, server ESAS 330 sends pxaxbqyayb*ka mod n to client ESAS305 who uses ka⁻¹ to get the shared secret key ks=pxaxbqyayb mod n.

In addition, once the shared secret key is established, non-invertibleKEP 340 uses photons and light phase shifting to protect sendingnon-invertible key 306 from client ESAS 305 to server ESAS 330. In oneembodiment, non-invertible KEP 340 uses two bases such as 0→|↑> and0→|→>. In this embodiment, server ESAS 330 maintains a 50% decodingerror rate and if the bases increase, so does the sampling rate. Afterall of the photons are shared between client ESAS 305 and server ESAS330, server ESAS 330 randomly chooses bases and decodes the signal.Next, client ESAS 305 provides the bases through the classical channeland, for any of the bases that do not match, client ESAS 305 discardsthe bits.

Non-invertible KEP 340 continues to provide enough samples to ensure thecorrect values are observed and that all of the base positions areeventually matched. If at any time a malicious user in the middle ofcommunication is discovered though detecting a phase shift change of thelight, indicating a malicious user in the middle, non-invertible KEP 340terminates and notifies upload site 335. As such, the original light isnot cloneable or storable without knowing the base used for decoding(see FIG. 7 and corresponding text for further details).

Server ESAS 330 sends a second portion of samples over the classicalchannel to client ESAS 305 to establish a second shared secret key(two-step authentication). Then, server ESAS 330 interfaces with clientESAS 305 over the classical channel using the second shared secret keyto decode the owner contact information.

In one embodiment, server ESAS 330 captures a screen shot of the uploadrequest and any other transaction details, and sends uploadauthorization request 345 to owner device 350 based on the owner contactinformation (e.g., mobile phone). The owner reviews upload authorizationrequest 345 and sends authorization response 360 to server ESAS 330,indicating whether the owner approves or disapproves of the uploadrequest.

Server ESAS 330 receives authorization response 360 and, whenauthorization response 360 indicates owner approval, server ESAS 330adds an “Authenticated” flag to secure file 310 and completes the uploadto upload site 335. If, however, authorization response 360 indicatesowner disapproval, then server ESAS 330 notifies upload requestingsystem 320 that the upload request is not approved (see FIG. 7 andcorresponding text for further details).

FIG. 4 is an exemplary diagram depicting encoded owner informationinserted into a file. Secure file 310 includes metadata 315, which isencoded with non-invertible key 306 and is not visible to a user. In oneembodiment, metadata 315 includes owner name 400 of secure file 310, theowner's contact information 410 (e.g., mobile phone, email address,etc.), and Security Authenticity Detection Flag (SADF) flag 420.

In one embodiment, the file owner's name and contact information arevalidated by respective trusted organizations (e.g., Government approvedTelecom Authority of respective countries). When validated, client ESAS305 sets SADF flag 420 to “Enabled”, indicating that secure file 310 issecure and server ESAS 330 should proceed through a security andauthorization process with client ESAS 305 when server ESAS 330 receivessecure file from upload requesting system 320.

FIG. 5 is an exemplary flowchart showing steps taken by an owner systemto create a secure file and upload the secure file to a cloud network.FIG. 5 processing commences at 500 whereupon, at step 510, client ESAS305 creates metadata with owner's personal information and a securityauthenticity detection flag (SADF) (see FIG. 4 and corresponding textfor further details).

At step 520, client ESAS 305 validates the owner's name and contactinformation by respective trusted organizations, and sets the SADF flagto “Enabled” upon validation. At step 530, client ESAS 305 encodes themetadata with a noninvertible key. At step 540, client ESAS 305 embedsencoded metadata 315 into secure file 310 and uploads secure file 310with encoded metadata 315 to cloud network 318. FIG. 5 processingthereafter ends at 550.

FIG. 6 is an exemplary flowchart showing steps taken by a serverEnhanced Security and Authenticity System (ESAS) to interface withclient ESAS 305 to obtain authorization by a file owner to upload afile. FIG. 6 processing commences at 600 whereupon, at step 610, serverESAS 330 receives upload request 322 from upload requesting system 320to upload secure file 310. For example, upload requesting system 320 maywish to upload a whitepaper from cloud network 318.

At predefined process 620, server ESAS 330 establishes a secure photonchannel and classical channel with client ESAS 305 and obtains ownercontact information over the secure channels using non-invertible KEP340. (see FIG. 7 and corresponding text for processing details).

Once server ESAS 330 decodes the owner contact information, server ESAS330, at step 630, captures a screen shot of the upload request and sendsupload authorization request 345, which includes the screen shot withtransaction details, to owner device 350 based on the decoded contactinformation. For example, the owner contact information may include amobile phone number or email address of the owner and server ESAS 330sends upload authorization request 345 to the owner's mobile phoneand/or email address. In one embodiment, the owner may negotiatefinancial terms with upload requesting system 320 and agree upon apayment amount to authorize the upload request.

At step 640, server ESAS 330 receives authorization response 360 fromowner device 350 indicating whether the owner approves or rejects theupload request by upload requesting system 320. At decision 650, serverESAS 330 determines as to whether the owner approved the upload request.If the owner approved the upload request, then decision 640 branches tothe ‘yes’ branch whereupon, at step 660, server ESAS 330 allows theupload of secure file 310 into upload site 335 and adds a separate“Authenticated” tag as a security checkmark to indicate the uploadedfile is successfully authenticated by the file owner. FIG. 6 processingthereafter ends at 670.

On the other hand, if the owner does not approve the upload request,then decision 640 branches to the ‘no’ branch whereupon, at step 680,server ESAS 330 sends a notification to upload requesting system 320that the upload request is rejected. FIG. 6 processing thereafter endsat 690.

FIG. 7 is an exemplary flowchart showing steps taken by a server ESAS tointerface with a client ESAS to establish a shared secret key and usethe shared secret key to send non-invertible key 306 over the photonchannel, which server ESAS 330 uses to decode metadata 315. FIG. 7server ESAS 330 processing commences at 700 whereupon, at step 710,server ESAS 330 looks up client ESAS 305 in database directory 310corresponding to secure file 310 in upload request 322.

At step 720, server ESAS 330 establishes a photon channel and classicalchannel with client ESAS 305 to perform non-invertible KEP 340. At step725, server ESAS 330 selects a base sampling number by analyzing thecontent of the secure file 310 to assess risk. At step 730, server ESAS330 factorizes the base number into prime numbers of the base sampling.At step 740, server ESAS 330 sends half of the refactored numbers (e.g.,combination of factorized base sampling numbers and prime numbers)through the photon channel to establish a first shared secret key.

Server ESAS 330 determines as to whether a malicious user in the middleattack is detected (decision 750). If a malicious user in the middleattack is detected, then decision 750 branches to the ‘yes’ branch whichloops back to step 760, whereby server ESAS 330 changes phase shift ofphoton light and proceeds through steps 725-740. This looping continuesuntil a malicious user in the middle attack is not detected, at whichpoint decision 750 branches to the ‘no’ branch exiting the loop.

At step 770, server ESAS 330 receives the non-invertible key 306 fromclient ESAS 305 over the photon channel and decodes non-invertible key306 using the first shared secret key from step 740 above. At step 780,server ESAS 330 sends the remaining half of the refactored numbersthrough the classical channel to establish a second shared secret key.At step 790, server ESAS 330 interfaces with client ESAS 305 over theclassical channel to decode the owner contact information using thesecond shared secret key. FIG. 7 processing thereafter returns to thecalling routine (see FIG. 6 ) at 795.

While particular embodiments of the present disclosure have been shownand described, it will be obvious to those skilled in the art that,based upon the teachings herein, that changes and modifications may bemade without departing from this disclosure and its broader aspects.Therefore, the appended claims are to encompass within their scope allsuch changes and modifications as are within the true spirit and scopeof this disclosure. Furthermore, it is to be understood that thedisclosure is solely defined by the appended claims. It will beunderstood by those with skill in the art that if a specific number ofan introduced claim element is intended, such intent will be explicitlyrecited in the claim, and in the absence of such recitation no suchlimitation is present. For non-limiting example, as an aid tounderstanding, the following appended claims contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimelements. However, the use of such phrases should not be construed toimply that the introduction of a claim element by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim element to disclosures containing only one suchelement, even when the same claim includes the introductory phrases “oneor more” or “at least one” and indefinite articles such as “a” or “an”;the same holds true for the use in the claims of definite articles.

The invention claimed is:
 1. A computer-implemented method comprising:receiving, at a server system, a request to upload a file comprisingmetadata that is encoded with a non-invertible key, wherein the metadatacomprises contact information corresponding to an owner of the file;establishing both a photon channel and a classical channel between theserver system and a client system, wherein the photon channel and theclassical channel are secured using one or more shared secret keys;selecting, by the server system, a base sampling number, by analyzing acontent of the file; factorizing the base sampling number into a set ofprime numbers by the server system, wherein the factorizing generates aset of refactored numbers; sending a first subset of the refactorednumbers from the server system to the client system over the photonchannel to establish a non-invertible key exchange protocolcommunication using a first one of the one or more shared secret keys;interfacing with the client system over the photon channel and theclassical channel to decode the contact information at the serversystem; sending an upload request from the server system to the owner ofthe file using the decoded contact information; and authorizing theupload request at the server system in response to receiving an uploadapproval from the owner.
 2. The computer-implemented method of claim 1further comprising: changing a phase shift of photon light to transmitover the photon channel in response to detecting a malicious user in themiddle attack while establishing the non-invertible key exchangeprotocol communication using the first shared secret key; selecting, bythe server system, a different base sampling number by further analyzingthe content of the file; factorizing the different base sampling numberinto a set of different prime numbers to generate a set of differentrefactored numbers; and sending a subset of the set of differentrefactored numbers from the server system to the client system over thephoton channel to establish a different non-invertible key exchangeprotocol communication using a different one of the one or more sharedsecret keys.
 3. The computer-implemented method of claim 1 furthercomprising: decoding, by the server system, the non-invertible key overthe photon channel using the first shared secret key; sending a secondsubset of the refactored numbers from the server system to the clientsystem over the classical channel to re-establish the non-invertible keyexchange protocol communication using a second one of the one or moreshared secret keys; and interfacing with the client system, by theserver system, over the classical channel using the second shared secretkey to decode the owner contact information.
 4. The computer-implementedmethod of claim 1 further comprising: comparing, by the client system,the first subset of the refactored numbers with a random set of bases;and discarding one or of the random set of bases that do not match atleast one of the first subset of the refactored numbers.
 5. Thecomputer-implemented method of claim 1 wherein, prior to receiving therequest to upload the file, the method further comprises: setting, bythe client system, a security authenticity detection flag in themetadata to a value of enabled in response to validating the ownercontact information by the client system; uploading the file comprisingthe encoded metadata to a cloud network; retrieving the file comprisingthe encoded metadata from the cloud network by an upload requestingsystem; and sending, by the upload requesting system, the request toupload the file to the server system.
 6. The method of claim 5 furthercomprising: sending the upload request to the owner of the file by theserver system in response to detecting the security authenticity flag isset to enabled; inserting an authenticated tag into the file in responseto authorizing the upload request; and uploading the file with theauthenticated flag to an upload site.
 7. An information handling systemcomprising: one or more processors; a memory coupled to at least one ofthe processors; a set of computer program instructions stored in thememory and executed by at least one of the processors in order toperform actions of: receiving, at a server system, a request to upload afile comprising metadata that is encoded with a non-invertible key,wherein the metadata comprises contact information corresponding to anowner of the file; establishing both a photon channel and a classicalchannel between the server system and a client system, wherein thephoton channel and the classical channel are secured using one or moreshared secret keys; selecting, by the server system, a base samplingnumber, by analyzing a content of the file; factorizing the basesampling number into a set of prime numbers by the server system,wherein the factorizing generates a set of refactored numbers; sending afirst subset of the refactored numbers from the server system to theclient system over the photon channel to establish a non-invertible keyexchange protocol communication using a first one of the one or moreshared secret keys; interfacing with the client system over the photonchannel and the classical channel to decode the contact information atthe server system; sending an upload request from the server system tothe owner of the file using the decoded contact information; andauthorizing the upload request at the server system in response toreceiving an upload approval from the owner.
 8. The information handlingsystem of claim 7 wherein the processors perform additional actionscomprising: changing a phase shift of photon light to transmit over thephoton channel in response to detecting a malicious user in the middleattack while establishing the first shared key; changing a phase shiftof photon light to transmit over the photon channel in response todetecting a malicious user in the middle attack while establishing thenon-invertible key exchange protocol communication using the firstshared secret key; selecting, by the server system, a different basesampling number by further analyzing the content of the file;factorizing the different base sampling number into a set of differentprime numbers to generate a set of different refactored numbers; andsending a subset of the set of different refactored numbers from theserver system to the client system over the photon channel to establisha different non-invertible key exchange protocol communication using adifferent one of the one or more shared secret keys.
 9. The informationhandling system of claim 7 wherein the processors perform additionalactions comprising: decoding, by the server system, the non-invertiblekey over the photon channel using the first shared secret key; sending asecond subset of the refactored numbers from the server system to theclient system over the classical channel to re-establish thenon-invertible key exchange protocol communication using a second one ofthe one or more shared secret keys; and interfacing with the clientsystem, by the server system, over the classical channel using thesecond shared secret key to decode the owner contact information. 10.The information handling system of claim 7 wherein the processorsperform additional actions comprising: comparing, by the client system,the first subset of the refactored numbers with a random set of bases;and discarding one or of the random set of bases that do not match atleast one of the first subset of the refactored numbers.
 11. Theinformation handling system of claim 7 wherein, prior to receiving therequest to upload the file, the processors perform additional actionscomprising: setting, by the client system, a security authenticitydetection flag in the metadata to a value of enabled in response tovalidating the owner contact information by the client system; uploadingthe file comprising the encoded metadata to a cloud network; retrievingthe file comprising the encoded metadata from the cloud network by anupload requesting system; and sending, by the upload requesting system,the request to upload the file to the server system.
 12. The informationhandling system of claim 11 wherein the processors perform additionalactions comprising: sending the upload request to the owner of the fileby the server system in response to detecting the security authenticityflag is set to enabled; inserting an authenticated tag into the file inresponse to authorizing the upload request; and uploading the file withthe authenticated flag to an upload site.
 13. A computer readablestorage medium storing a computer program product comprising computerprogram code that, when executed by an information handling system,causes the information handling system to perform actions comprising:receiving, at a server system, a request to upload a file comprisingmetadata that is encoded with a non-invertible key, wherein the metadatacomprises contact information corresponding to an owner of the file;establishing both a photon channel and a classical channel between theserver system and a client system, wherein the photon channel and theclassical channel are secured using one or more shared secret keys;selecting, by the server system, a base sampling number, by analyzing acontent of the file; factorizing the base sampling number into a set ofprime numbers by the server system, wherein the factorizing generates aset of refactored numbers; sending a first subset of the refactorednumbers from the server system to the client system over the photonchannel to establish a non-invertible key exchange protocolcommunication using a first one of the one or more shared secret keys;interfacing with the client system over the photon channel and theclassical channel to decode the contact information at the serversystem; sending an upload request from the server system to the owner ofthe file using the decoded contact information; and authorizing theupload request at the server system in response to receiving an uploadapproval from the owner.
 14. The computer readable storage medium ofclaim 13 wherein the information handling system performs furtheractions comprising: changing a phase shift of photon light to transmitover the photon channel in response to detecting a malicious user in themiddle attack while establishing the non-invertible key exchangeprotocol communication using the first shared secret key; selecting, bythe server system, a different base sampling number by further analyzingthe content of the file; factorizing the different base sampling numberinto a set of different prime numbers to generate a set of differentrefactored numbers; and sending a subset of the set of differentrefactored numbers from the server system to the client system over thephoton channel to establish a different non-invertible key exchangeprotocol communication using a different one of the one or more sharedsecret keys.
 15. The computer readable storage medium of claim 13wherein the information handling system performs further actionscomprising: decoding, by the server system, the non-invertible key overthe photon channel using the first shared secret key; sending a secondsubset of the refactored numbers from the server system to the clientsystem over the classical channel to re-establish the non-invertible keyexchange protocol communication using a second one of the one or moreshared secret keys; and interfacing with the client system, by theserver system, over the classical channel using the second shared secretkey to decode the owner contact information.
 16. The computer readablestorage medium of claim 13 wherein the information handling systemperforms further actions comprising: comparing, by the client system,the first subset of the refactored numbers with a random set of bases;and discarding one or of the random set of bases that do not match atleast one of the first subset of the refactored numbers.
 17. Thecomputer readable storage medium of claim 13 wherein, prior to receivingthe request to upload the file, the information handling system performsfurther actions comprising: setting, by the client system, a securityauthenticity detection flag in the metadata to a value of enabled inresponse to validating the owner contact information by the clientsystem; uploading the file comprising the encoded metadata to a cloudnetwork; retrieving the file comprising the encoded metadata from thecloud network by an upload requesting system; sending, by the uploadrequesting system, the request to upload the file to the server system.